Very cool!! I think a lot of this may be out of scope for this module, though, which is just trying to be specific to webgl.

What about moving the core non-glsl logic to another module like 'js-glsl'? Then you can build other modules on top of it.

Thanks!

Sent from my iPhone

On Mar 10, 2016, at 3:13 AM, Deema Yvanow notifications@github.com wrote:

Hello @mattdesl!

There I’ve provided nogl implementation of a module for nodejs.
Augmented the API to follow the logic createDraw(shader, options). It is compatible with old API, but now user can simply pass a fragment shader source: create(glslify('sound.frag')).
Optimized performance of draw, now it is 2-3 times faster in some cases.
Turned on float values by default.
I know, it is quite big change, just wanted to know your opinion and maybe ideas for a new package name, if you prefer to keep the current gl-shader-output implementation. Maybe gl-shader-process or gl-shader-draw?

You can view, comment on, or merge this pull request online at:

#2

Commit Summary

Update style
Provide basic nogl implementation
File Changes

M README.md (48)
M index.js (168)
A nogl.js (55)
M package.json (28)
M test/test.js (177)
Patch Links:

https://github.com/Jam3/gl-shader-output/pull/2.patch
https://github.com/Jam3/gl-shader-output/pull/2.diff
—
Reply to this email directly or view it on GitHub.

@mattdesl nice idea, thanks. Guess I will do that. I have already a bunch of things which are able to be implemented with glsl-js stackgl/glsl-transpiler#9

Moved nogl logic to nogl-shader-output

Obsolete due to #3